-
Notifications
You must be signed in to change notification settings - Fork 91
ENH: Add support to find Headers in Apple Frameworks #448
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
ENH: Add support to find Headers in Apple Frameworks #448
Conversation
Add specific framework path handling Refactor include directory parsing to support multiple candidate paths for headers and introduce macOS-specific logic for resolving framework-relative header paths. Enhance generator flexibility and robustness for cross-platform usage. Push upstream fix via: danmar/simplecpp#448
Thanks for your contribution.
|
It might be a few weeks before I circle back to push changes upstream. |
ok thanks understood.. for your information we have a PR to start using C++11 so if you get back in few weeks I will hopefully not complain about you using C++11 at least. |
Add specific framework path handling Refactor include directory parsing to support multiple candidate paths for headers and introduce macOS-specific logic for resolving framework-relative header paths. Enhance generator flexibility and robustness for cross-platform usage. Push upstream fix via: danmar/simplecpp#448
Add specific framework path handling Refactor include directory parsing to support multiple candidate paths for headers and introduce macOS-specific logic for resolving framework-relative header paths. Enhance generator flexibility and robustness for cross-platform usage. Push upstream fix via: danmar/simplecpp#448
Add specific framework path handling Refactor include directory parsing to support multiple candidate paths for headers and introduce macOS-specific logic for resolving framework-relative header paths. Enhance generator flexibility and robustness for cross-platform usage. Push upstream fix via: danmar/simplecpp#448
The header locations in apple frameworks require manipulation of the directory name in a '<pkg/myhdr.h>' include defintion. The header file is located at <pkg.framework/Headers/myhdr.h> in a framework.
This is an outline of a test. The test currently fails. I could not figure out how these tests are working. I would greatly appreciate a little help to understand how to use the test framework.
31bffbf
to
de9d233
Compare
@danmar I have updated this PR, but I am struggling to figure out how to make a test to exercise this code. I tried to decipher how other tests were working, but could not identify how the "cache" would need to be setup to test the new functionality. Any guidance would be greatly appreciated. Thanks, |
@glankk Thank you for the C++11 updates! This is great work! This PR is adjacent to some code that you recently refactored. It would be great to have your input. Thanks, |
I suggest we emulate gcc's darwin-specific |
I will go on vacation for a week. Please ping me later if you want review.. |
The header locations in apple frameworks require manipulation of the directory name in a '<pkg/myhdr.h>' include defintion.
The header file is located at <pkg.framework/Headers/myhdr.h> in a framework.